Making Agile Development Work in a Government Contracting Environment - Measuring velocity with Earned Value

Before any of the current “agile” development methods, Earned Value Management provided information for planning and controlling complex projects by measuring how much “value” was produced for a given cost in a period of time. One shortcoming of an agile development method is its inability to forecast the future cost and schedule of the project beyond the use of “yesterdays weather” metrics. These agile methods assume the delivered value, “velocity” in the case of XP, is compared with the estimated value – this is a simple comparison between budget and actual cost resulting in a Cost Variance. No Schedule Variance process is directly available in XP. Earned Value Analysis provides a means of predicting future schedule and cost variances through three measurements – budgeted cost for work scheduled, actual cost for work performed, and budgeted cost for work performed (earned value). This paper describes the use of Earned Value in conjunction with Agile Development on a mission-critical, high-security, government project.